Expire authentication tokens #7140
Draft
+120
−24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
from
701dafe to
30a434b
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
2 times, most recently
from
e8ff198 to
071b35a
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
2 times, most recently
from
b6d01bd to
0b8c3ca
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
2 times, most recently
from
54eb0b1 to
18c5fb0
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
2 times, most recently
from
904e5a3 to
d8c237b
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
from
18c5fb0 to
3e6c621
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
from
d8c237b to
6d9ce24
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
2 times, most recently
from
0310a22 to
1e9c0e9
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
from
6d9ce24 to
b91322a
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
from
1e9c0e9 to
9af5cbe
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
2 times, most recently
from
49f6b8d to
83a9265
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
from
9af5cbe to
2c3004d
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
from
2c3004d to
5d35ac2
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
2 times, most recently
from
45c2c57 to
8886ac4
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
2 times, most recently
from
6f67e0e to
cb19c82
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
from
8886ac4 to
c64ea59
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
from
cb19c82 to
297d6aa
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
from
c64ea59 to
9086f0f
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
from
297d6aa to
d69155e
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
from
9086f0f to
1871031
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
from
d69155e to
273c547
Compare
link2xt
force-pushed
the
link2xt/ykltkokxntvk
branch
from
1871031 to
f5d3f7f
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
3 times, most recently
from
312c7c8 to
0f1c10f
Compare
link2xt
force-pushed
the
link2xt/expire-auth-tokens
branch
from
0f1c10f to
10b2b85
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on #7116
Closes #5126
Still need to make QR withdrawal work. If we generate new auth codes each time, then when we withdraw some QR code, we will withdraw invite code that may have been used by many QR codes. One option would be to also generate a new invite code for each QR. Or we can remove withdrawal via scanning own QR and make a dedicated API to reset all QR codes for some group or for contact setup.